home *** CD-ROM | disk | FTP | other *** search
- Path: asterix.urc.tue.nl!buex95a
- From: buex95a@asterix.urc.tue.nl (Marcel van Kervinck)
- Newsgroups: comp.sys.amiga.programmer
- Subject: Re: Amiga Memory Map Needed!!!
- Date: 31 Jan 1996 15:29:13 GMT
- Organization: Eindhoven University of Technology, The Netherlands
- Distribution: world
- Message-ID: <4eo1s9$im3@tuegate.tue.nl>
- References: <4dl0pe$1jr0@serra.unipi.it> <13213494@sourcery.han.de>
- NNTP-Posting-Host: asterix.urc.tue.nl
- X-Newsreader: TIN [version 1.2 PL2]
-
- Olaf Barthel (olsen@sourcery.han.de) wrote:
- : >
- : > Ok, so location $4 points to EXEC, but:
- : >
- : > 1) I wonder: why not 0?
-
- : Careful please, this is something completely different. The data
- : structures and programming guidelines are documented only in the RKMs.
- : Unfortunately, these are hard to obtain at the moment. I'm afraid I
- : can't provide any help here :(
-
- The system's commented include files are useful too.
-
- BTW: Why doesn't anyone wonder why there is need for execbase
- to be located in a fixed address at all? When I started
- programming the amiga this really struck me. I you take
- the step to completely dynamically manage your memory, why
- not take the final step and remove the need for $4 as well?
-
- After all, execbase should be passed to any task at startup.
- Or even better, the task that spawns a task should be _able_
- to pass anything to it's child. Usually this is done by
- setting the initial stack frame. If execbase is needed by
- the new task, it should be there. And not in $4. That is
- a bit perverse.
-
- Comments?
-
- Marcel
- -- _ _
- _| |_|_|
- |_ |_ Marcel van Kervinck
- |_| buex95a@urc.tue.nl
-